This is a creation in
Article, where the information may have evolved or changed.
All the places involved in storage are very prone to "pits", Kubernetes is no exception.
First, the cause of the problem
The problem began yesterday by upgrading the operation of a stateful service. The pod under the service is mounted with a persistent Volume provided with Ceph RBD. The pod is deployed with normal deployment and does not use the Petset in Alpha state. T
Windows dynamic disk volumes: configuration operations for simple volumes, cross-zone volumes, with-zone volumes, image volumes, and RAID 5 volumes
Windows Server 2003 provides a new disk management method to improve disk performa
Windows Server 2003 provides new ways to manage disk and improve disk performance and fault tolerance. Upgrading basic disks to dynamic disks gives you more flexibility in allocating and managing disk space and enabling you to configure various disk arrays to improve disk capacity.Dynamic disks with the Basic Disk Compare :A basic disk can contain only 4 partitions, which are up to three primary partitions and one extended partition, and the extended partition can contain several logical disks.
To configure failover clustering for customers today, on Windows Server R2 systems, after Dell storage on the iSCSI connection, you can find new simple volumes, spanned volumes, striped volumes, mirrored volumes, RAID-5 volumes, and so on in Disk Management: Have never touc
do RAID-5 volume, set the volume labeled H: ()650) this.width=650; "src="%5c "alt=" \ "wkiol1uyn_bznzuvaaktfwmow6c822.jpg\" "/>7. Turn off the virtual machine, remove Disk 3, and add a fast new disk. ()650) this.width=650; "src="%5c "alt=" \ "wkiom1uynqchs9a_aae7fdrkihm479.jpg\" "/>8. Start the virtual machine and fix the F volume (RAID-0 volume). ()650) this.width=650; "src="%5c "alt=" \ "wkiol1uyn_ftdrhgaakaw1txkgg245.jpg\" "/>9. Start the virtual machine and fix the H volume (RAID-5 volume).
Hard disk partition, there are three kinds, primary partition, extended partition, logical partitionA hard disk primary partition has at least 1, a maximum of 4, and an extended partition can be no more than 1. and the primary partition + extended partition must not exceed 4 total. A logical partition can have several.The extended partition cannot be used directly, it must be used to separate the logical partition, and the logical partition exists in the extended partition. Logical partitions ar
LVM is a mechanism for managing disk partitions in a Linux environment, a logical layer that is built on top of hard disks and partitions and under a file system to improve the flexibility of disk partition management. The biggest advantage is that the size of the storage space is adjusted without compromising the data.This article focuses on the creation of LVM, the expansion and reduction of LVM, and the use of snapshot volumes three partsPart I: Cr
process into the appropriate pod, making it a container (Container) that runs in the pod. to establish the relationship between service and pod, kubernetes first labels each pod and then assigns a label selector (label Selector) to the corresponding service. This cleverly solves the problem of service-pod correlation. Pod:pod runs in the node environment, which can be a physical machine or a virtual machine that can be a public or private cloud , typ
. Main concepts of Kubernetes 2.1 Pods
In the Kubernetes system, the smallest granularity of scheduling is not simply a container, but a Pod. A Pod is the smallest deployment unit that can be created, destroyed, scheduled, and managed. One or more containers (Container) constitute a Pod. Generally, the containers in the Pod run the same application. Pods contain containers running on the same Minion (Host)
Kubeconfig file
Now that we want dashboard to use the Kubeconfig file, we need to modify the configuration information in the Dashboard-controller.yaml file that involves containers:
spec: containers: - name: kubernetes-dashboard image: mritd/kubernetes-dashboard-amd64:v1.4.0 volumeMounts: - mountPath: /srv/kubernetes
functions are as follows:
1 Use Docker for application wrapping (package), instantiating (instantiate), running (run).
2 to run and manage the containers across the machine in a cluster manner.
3 to solve the communication problem between Docker and cross machine containers.
4 Kubernetes's self-healing mechanism makes the container cluster always run in the user's desired state.
The current kubernetes support GCE, Vshpere, CoreOS, OpenShift, Azure an
associated containers into a pod, usually in pod containers running the same application. Pods contain containers that run on the same minion (Host), as a single snap-in that shares the same volumes and network NAMESPACE/IP and port space.3.2. ServicesServices is also the basic operating unit of Kubernetes, is the abstraction of real application services, each service has a lot of corresponding containers
seem to work ). The Kubernetes cluster depends on two third-party components: etcd and docker. The former provides status storage, and the two are used to manage containers. Clusters can also use distributed storage to provide storage space for containers. Displays the components of the current system:
Kubernetes proxy nodes Kubelet and Kube-proxy run on the proxy node. They listen to Service node informa
, destroyed, dispatched, and managed. The associated one or more containers (Container) Form a pod, usually in pod containers running the same application. Pods contain containers that run on the same minion (Host), as a single snap-in that shares the same volumes and network NAMESPACE/IP and port space.2.2 ServicesServices is also the basic operating unit of Kubernetes, is the abstraction of real applicati
can be said to be a big innovation, providing a model of a combination of containers.2.1 Basic Operations
Create
Kubectl create-f Xxx.yaml
Inquire
Kubectl Get pod YourpodnameKubectl describe pod yourpodname
Delete
Kubectl Delete pod Yourpodname
Update
Kubectl Replace/path/to/yournewyaml.yaml
2.2 Pods and containersIn Docker, the container is the smallest processing unit, adding and deleting the object is
Shuffle service can be shared by the performer who belongs to a different sparkjobs.
A sample configuration file, Conf/kubernetes-shuffle-service.yaml, can be tailored to a specific cluster as needed. Note that it is important to properly set up spec.template.metadata.labels for the Shuffle service, because there may be more than one Shuffle service instance running in the cluster. These tags provide a way for the Spark application to locate the spec
rangeIPC Namespaces: Multiple containers in the pod can communicate using SYSTEMV IPC or POSIX Message Queuing.UTS namespace: Multiple containers in the pod share a host name.Volumes (Shared storage volume): Each container in the pod can access the Volumes defined at the pod level.LabelLabel is a core concept in the kubernetes system. Labels are attached to various objects in the form of Key/value key-valu
Using the Docker process, we need to look at the data generated in the container, and between the container and the container, the container and the host before the data sharing, backup and other operations, where the data management of the container. The management of data currently provides the following two ways:#数据卷 Data Volumes#数据卷容器 Data Volumes containers
One, data volumeA data volume, in a way that
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.